Skip to content

docs: add OpenVEX document and wire into Trivy scans (OSPS-VM-04.02)#91

Merged
paradoxbound merged 1 commit into
mainfrom
docs/vex-document
Mar 9, 2026
Merged

docs: add OpenVEX document and wire into Trivy scans (OSPS-VM-04.02)#91
paradoxbound merged 1 commit into
mainfrom
docs/vex-document

Conversation

@paradoxbound
Copy link
Copy Markdown
Owner

Summary

  • Adds vex.json at repo root in OpenVEX format
  • Passes --vex vex.json to both Trivy image scan invocations (PR gate and release gate) so confirmed non-applicable CVEs are automatically suppressed
  • Documents the VEX document, its purpose, and how to add statements in SECURITY.md
  • Satisfies OSPS-VM-04.02

How it works

When a CVE is flagged in a dependency but does not affect this project (e.g. a code path never called, or a dev dependency not in the Docker image), a statement is appended to vex.json with a justification. Trivy reads it on every scan run.

Test plan

  • Review vex.json and SECURITY.md changes
  • Confirm docker-publish.yml Trivy invocations both include --vex vex.json
  • Approve and merge

Generated with Claude Code

Adds vex.json in OpenVEX format to track vulnerabilities in dependencies
that do not affect the deployed product. Trivy --vex flag is added to both
PR and release scan invocations so confirmed non-applicable CVEs are
automatically suppressed from gate failures. Documents the VEX process
and statement format in SECURITY.md.

Signed-off-by: Paradoxbound <paradoxbound@users.noreply.github.com>
@paradoxbound paradoxbound merged commit 14f463c into main Mar 9, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants